I have a problem with integration an ASP.NET CORE 5.0 web application with OKTA. My company needs all web apps to be integrated with OKTA. This app I wrote about is hosted on Fargate cluster as Linux container (and will use Application Load Balancer + AWS certificate to use HTTPS). Container runs on HTTP and it's redirected to HTTPS by ALB. I am fighting the dreaded 400 Bad Request Error: The 'redirect_uri' parameter must be a Login redirect URI in the client app settings My Maven parent is spring-boot-starter-parent 3.3.2 and I've declared okta-spring-boot-starter 3.0.7 as a dependency. My SecurityFilterChain is pretty basic. I want everything to be behind an Okta auth. I would like to get other info from Okta, because with this.props.auth.getUser () I’ll receive only email, name and surname about user. But there are many data on Okta for example state, city, street address, zip code and so on. Hello Okta Community, I’m currently integrating Okta OpenID Connect (OIDC) authentication in an ASP.NET Core application. I’ve configured the Okta app settings and provided the necessary redirect URIs, but I’m running into an issue where the redirect_uri in the authentication request defaults to HTTP instead of HTTPS. Okta API - authn always returns Invalid Session Ask Question Asked 11 years, 7 months ago Modified 9 months ago I added a ‘Login with Okta’ button on my SPA using oktaAuth.signInWithRedirect, but it didn’t redirect back to the redirectUri after I logged in on the Okta login page. To customize Okta application loading screen, please follow below steps: Login to your Okta organization Go to Admin tab Click on Setting From Setting drop down menu select Appearance, here you can configure Application Theme, Sign-in configuration, organization logo. 3- User gets redirected to Okta to enter their username in Okta Login Page 4 - User enter their username (External IdP username) in Okta Login page 5 - User get logged in to the OIDC app. Is there a way to bypass 3 & 4? (We’re aware that we can use the routing rules for IPs) Please let us know if there are any methods to achieve this. Now even if I delete the users and have them try to login, they are not JIT created. They get that “User canceled the social login request” response from their external IDP. Since our Okta users can still login to our Web apps using the (Okta auth) (thanks to internet god). I’m taking this precious time to take a decision with concerned businesses as to Drop OKTA for now (cheap solution) or create and configure a new account (wich is gonna be costy and a pain).